-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PXY-860 Add metadata to Plugins #67
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a description of the change ?
Also a question regarding format and loading with multiple plugins
|
||
default List<String> examples() { | ||
try { | ||
return List.of(resourceAsString("/META-INF/services/example.json")); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Configuration is done by yaml from configuration file in gateway. Maybe we should provide multiple configuration files.
Also if multiple plugins (let's say 2) are loaded in the classpath and each ref a /META-INF/services/example.json
what happen ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, addressed here: 84033e0
@fteychene good? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@framiere - what's the behaviour for;
|
|
If the purpose of this is for the UI then it must contain an example JSON, otherwise it's useless imo. Can we do another PR that covers this? |
The objective is to be able to give more context for each plugin.
Any UI wanted to surface these plugins will need a way to get some metadata about them.